Variable transport data retention and deletion

ABSTRACT

An example operation includes one or more of encrypting, by a transport, received data based on a first biometric associated with an occupant, unencrypting, by the transport, the encrypted data, based on a verification of a second biometric, wherein the second biometric is a continuum of the first biometric, and providing, by the transport, the unencrypted data to the occupant.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. non-provisional patent application Ser. No. 16/925,121 entitled, “VARIABLE TRANSPORT DATA RETENTION AND DELETION” filed Jul. 9, 2020 which is related to U.S. non-provisional patent application Ser. No. 16/925,091 entitled, “DYNAMICALLY ADAPTING DRIVING MODE SECURITY CONTROLS” filed Jul. 9, 2020 and each is incorporated herein by reference in its entirety.

BACKGROUND

Vehicles or transports, such as cars, motorcycles, trucks, planes, trains, etc., generally provide transportation needs to occupants and/or goods in a variety of ways. Functions related to transports may be identified and utilized by various computing devices, such as a smartphone or a computer located on and/or off the transport.

SUMMARY

One example embodiment provides a method that includes one or more of encrypting, by a transport, received data based on a first biometric associated with an occupant, unencrypting, by the transport, the encrypted data, based on a verification of a second biometric, wherein the second biometric is a continuum of the first biometric, and providing, by the transport, the unencrypted data to the occupant.

Another example embodiment provides a transport including a processor configured to provide one or more of encrypt received data based on a first biometric associated with an occupant, unencrypt the encrypted data, based on a verification of a second biometric, wherein the second biometric is a continuum of the first biometric, and provide the unencrypted data to the occupant.

Still yet another example embodiment includes a non-transitory computer readable medium comprising instructions, that when read by a processor, cause the processor to perform one or more of encrypting, by a transport, received data based on a first biometric associated with an occupant, unencrypting, by the transport, the encrypted data, based on a verification of a second biometric, wherein the second biometric is a continuum of the first biometric, and providing, by the transport, the unencrypted data to the occupant.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates an example system communication diagram of data management among a transport, a data source server and a user interface device, according to example embodiments.

FIG. 1B illustrates a further example of data security management and distribution, according to example embodiments.

FIG. 1C illustrates an example of a hand gesture biometric being performed in the transport, according to example embodiments.

FIG. 1D illustrates a further example of a hand gesture biometric being performed in the transport, according to example embodiments.

FIG. 2A illustrates a transport network diagram, according to example embodiments.

FIG. 2B illustrates another transport network diagram, according to example embodiments.

FIG. 2C illustrates yet another transport network diagram, according to example embodiments.

FIG. 2D illustrates a further transport network diagram, according to example embodiments.

FIG. 2E illustrates yet a further transport network diagram, according to example embodiments.

FIG. 2F illustrates a diagram depicting electrification of one or more elements, according to example embodiments.

FIG. 2G illustrates a diagram depicting interconnections between different elements, according to example embodiments.

FIG. 2H illustrates a further diagram depicting interconnections between different elements, according to example embodiments.

FIG. 2I illustrates yet a further diagram depicting interconnections between elements, according to example embodiments.

FIG. 3A illustrates a flow diagram, according to example embodiments.

FIG. 3B illustrates another flow diagram, according to example embodiments.

FIG. 3C illustrates yet another flow diagram, according to example embodiments.

FIG. 4 illustrates a machine learning transport network diagram, according to example embodiments.

FIG. 5A illustrates an example vehicle configuration for managing database transactions associated with a vehicle, according to example embodiments.

FIG. 5B illustrates another example vehicle configuration for managing database transactions conducted among various vehicles, according to example embodiments

FIG. 6A illustrates a blockchain architecture configuration, according to example embodiments.

FIG. 6B illustrates another blockchain configuration, according to example embodiments.

FIG. 6C illustrates a blockchain configuration for storing blockchain transaction data, according to example embodiments.

FIG. 6D illustrates example data blocks, according to example embodiments.

FIG. 7 illustrates an example system that supports one or more of the example embodiments.

DETAILED DESCRIPTION

It will be readily understood that the instant components, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of at least one of a method, apparatus, non-transitory computer readable medium and system, as represented in the attached figures, is not intended to limit the scope of the application as claimed but is merely representative of selected embodiments.

The instant features, structures, or characteristics as described throughout this specification may be combined in any suitable manner in one or more embodiments. For example, the usage of the phrases “example embodiments”, “some embodiments”, or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment. Thus, appearances of the phrases “example embodiments”, “in some embodiments”, “in other embodiments”, or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the diagrams, any connection between elements can permit one-way and/or two-way communication even if the depicted connection is a one-way or two-way arrow. In the current solution, a transport may include one or more of cars, trucks, walking area battery electric vehicle (BEV), e-Palette, fuel cell bus, motorcycles, scooters, bicycles, boats, recreational vehicles, planes, and any object that may be used to transport people and or goods from one location to another.

In addition, while the term “message” may have been used in the description of embodiments, other types of network data, such as, a packet, frame, datagram, etc. may also be used. Furthermore, while certain types of messages and signaling may be depicted in exemplary embodiments they are not limited to a certain type of message and signaling.

Example embodiments provide methods, systems, components, non-transitory computer readable media, devices, and/or networks, which provide at least one of: a transport (also referred to as a vehicle or car herein), a data collection system, a data monitoring system, a verification system, an authorization system and a vehicle data distribution system. The vehicle status condition data, received in the form of communication messages, such as wireless data network communications and/or wired communication messages, may be processed to identify vehicle/transport status conditions and provide feedback as to the condition and/or changes of a transport. In one example, a user profile may be applied to a particular transport/vehicle to authorize a current vehicle event, service stops at service stations, to authorize subsequent vehicle rental services, and enable vehicle to vehicle communications.

Within the communication infrastructure, a decentralized database is a distributed storage system, which includes multiple nodes that communicate with each other. A blockchain is an example of a decentralized database, which includes an append-only immutable data structure (i.e. a distributed ledger) capable of maintaining records between untrusted parties. The untrusted parties are referred to herein as peers, nodes or peer nodes. Each peer maintains a copy of the database records and no single peer can modify the database records without a consensus being reached among the distributed peers. For example, the peers may execute a consensus protocol to validate blockchain storage entries, group the storage entries into blocks, and build a hash chain via the blocks. This process forms the ledger by ordering the storage entries, as is necessary, for consistency. In a public or permissionless blockchain, anyone can participate without a specific identity. Public blockchains can involve crypto-currencies and use consensus based on various protocols such as proof of work (PoW). Conversely, a permissioned blockchain database can secure interactions among a group of entities, which share a common goal, but which do not or cannot fully trust one another, such as businesses that exchange funds, goods, information, and the like. The instant solution can function in a permissioned and/or a permissionless blockchain setting.

Smart contracts are trusted distributed applications, which leverage tamper-proof properties of the shared or distributed ledger (which may be in the form of a blockchain) and an underlying agreement between member nodes, which is referred to as an endorsement or endorsement policy. In general, blockchain entries are “endorsed” before being committed to the blockchain while entries, which are not endorsed are disregarded. A typical endorsement policy allows smart contract executable code to specify endorsers for an entry in the form of a set of peer nodes that are necessary for endorsement. When a client sends the entry to the peers specified in the endorsement policy, the entry is executed to validate the entry. After validation, the entries enter an ordering phase in which a consensus protocol is used to produce an ordered sequence of endorsed entries grouped into blocks.

Nodes are the communication entities of the blockchain system. A “node” may perform a logical function in the sense that multiple nodes of different types can run on the same physical server. Nodes are grouped in trust domains and are associated with logical entities that control them in various ways. Nodes may include different types, such as a client or submitting-client node, which submits an entry-invocation to an endorser (e.g., peer), and broadcasts entry-proposals to an ordering service (e.g., ordering node). Another type of node is a peer node, which can receive client submitted entries, commit the entries and maintain a state and a copy of the ledger of blockchain entries. Peers can also have the role of an endorser. An ordering-service-node or orderer is a node running the communication service for all nodes, and which implements a delivery guarantee, such as a broadcast to each of the peer nodes in the system when committing entries and modifying a world state of the blockchain. The world state can constitute the initial blockchain entry, which normally includes control and setup information.

A ledger is a sequenced, tamper-resistant record of all state transitions of a blockchain. State transitions may result from smart contract executable code invocations (i.e., entries) submitted by participating parties (e.g., client nodes, ordering nodes, endorser nodes, peer nodes, etc.). An entry may result in a set of asset key-value pairs being committed to the ledger as one or more operands, such as creates, updates, deletes, and the like. The ledger includes a blockchain (also referred to as a chain), which is used to store an immutable, sequenced record in blocks. The ledger also includes a state database, which maintains a current state of the blockchain. There is typically one ledger per channel. Each peer node maintains a copy of the ledger for each channel of which they are a member.

A chain is an entry log structured as hash-linked blocks, and each block contains a sequence of N entries where N is equal to or greater than one. The block header includes a hash of the blocks' entries, as well as a hash of the prior block's header. In this way, all entries on the ledger may be sequenced and cryptographically linked together. Accordingly, it is not possible to tamper with the ledger data without breaking the hash links. A hash of a most recently added blockchain block represents every entry on the chain that has come before it, making it possible to ensure that all peer nodes are in a consistent and trusted state. The chain may be stored on a peer node file system (i.e., local, attached storage, cloud, etc.), efficiently supporting the append-only nature of the blockchain workload.

The current state of the immutable ledger represents the latest values for all keys that are included in the chain entry log. Since the current state represents the latest key values known to a channel, it is sometimes referred to as a world state. Smart contract executable code invocations execute entries against the current state data of the ledger. To make these smart contract executable code interactions efficient, the latest values of the keys may be stored in a state database. The state database may be simply an indexed view into the chain's entry log and can therefore be regenerated from the chain at any time. The state database may automatically be recovered (or generated if needed) upon peer node startup, and before entries are accepted.

A blockchain is different from a traditional database in that the blockchain is not a central storage but rather a decentralized, immutable, and secure storage, where nodes must share in changes to records in the storage. Some properties that are inherent in blockchain and which help implement the blockchain include, but are not limited to, an immutable ledger, smart contracts, security, privacy, decentralization, consensus, endorsement, accessibility, and the like.

Example embodiments provide a service to a particular vehicle and/or a user profile that is applied to the vehicle. For example, a user may be the owner of a vehicle or the operator of a vehicle owned by another party. The vehicle may require service at certain intervals and the service needs may require authorization prior to permitting the services to be received. Also, service centers may offer services to vehicles in a nearby area based on the vehicle's current route plan and a relative level of service requirements (e.g., immediate, severe, intermediate, minor, etc.). The vehicle needs may be monitored via one or more vehicle and/or road sensors or cameras, which report sensed data to a central controller computer device in and/or apart from the vehicle. This data is forwarded to a management server for review and action. A sensor may be located on one or more of the interior of the transport, the exterior of the transport, on a fixed object apart from the transport, and on another transport proximate the transport. The sensor may also be associated with the transport's speed, the transport's braking, the transport's acceleration, fuel levels, service needs, the gear-shifting of the transport, the transport's steering, and the like. A sensor, as described herein, may also be a device, such as a wireless device in and/or proximate to the transport. Also, sensor information may be used to identify whether the vehicle is operating safely and whether an occupant has engaged in any unexpected vehicle conditions, such as during a vehicle access and/or utilization period. Vehicle information collected before, during and/or after a vehicle's operation may be identified and stored in a transaction on a shared/distributed ledger, which may be generated and committed to the immutable ledger as determined by a permission granting consortium, and thus in a “decentralized” manner, such as via a blockchain membership group.

Each interested party (i.e., owner, user, company, agency, etc.) may want to limit the exposure of private information, and therefore the blockchain and its immutability can be used to manage permissions for each particular user vehicle profile. A smart contract may be used to provide compensation, quantify a user profile score/rating/review, apply vehicle event permissions, determine when service is needed, identify a collision and/or degradation event, identify a safety concern event, identify parties to the event and provide distribution to registered entities seeking access to such vehicle event data. Also, the results may be identified, and the necessary information can be shared among the registered companies and/or individuals based on a consensus approach associated with the blockchain. Such an approach could not be implemented on a traditional centralized database.

Various driving systems of the instant solution can utilize software, an array of sensors as well as machine learning functionality, light detection and ranging (LIDAR) projectors, radar, ultrasonic sensors, etc. to create a map of terrain and road that a transport can use for navigation and other purposes. In some embodiments, GPS, maps, cameras, sensors and the like can also be used in autonomous vehicles in place of LIDAR.

The instant solution includes, in certain embodiments, authorizing a vehicle for service via an automated and quick authentication scheme. For example, driving up to a charging station or fuel pump may be performed by a vehicle operator or an autonomous transport and the authorization to receive charge or fuel may be performed without any delays provided the authorization is received by the service and/or charging station. A vehicle may provide a communication signal that provides an identification of a vehicle that has a currently active profile linked to an account that is authorized to accept a service, which can be later rectified by compensation. Additional measures may be used to provide further authentication, such as another identifier may be sent from the user's device wirelessly to the service center to replace or supplement the first authorization effort between the transport and the service center with an additional authorization effort.

Data shared and received may be stored in a database, which maintains data in one single database (e.g., database server) and generally at one particular location. This location is often a central computer, for example, a desktop central processing unit (CPU), a server CPU, or a mainframe computer. Information stored on a centralized database is typically accessible from multiple different points. A centralized database is easy to manage, maintain, and control, especially for purposes of security because of its single location. Within a centralized database, data redundancy is minimized as a single storing place of all data also implies that a given set of data only has one primary record. A blockchain may be used for storing transport-related data and transactions.

FIG. 1A illustrates an example system communication diagram of data management according to example embodiments. Referring to FIG. 1A, the system 100 includes a server 110, a transport 120 and a user interface/device 130. In operation, a transport 120 may receive data 114 from a server 110 as a result of a request sent or as a periodic update to an active occupant profile or transport profile that is registered to receive periodic data updates. The data may be received in response to an initiation message from a user device, such as an occupant of the transport operating the transport computer or their own device. The data request may be a user initiated request, such as a voice request or gesture made to request certain data, such as notification updates, navigation data, purchase order information, emails, text messages, a virtual media dashboard, etc. The transport 120 may identify the received data 114 and may seek to authenticate an occupant via a first biometric 116, which may be input by a gesture sensor, an audio sensor, a touch sensor, a motion detection sensor, etc., that is integrated with the user interface 130.

Once the data is received and the first biometric is identified 116, the transport 120 may use an internal computing device to process the first biometric for accuracy based on a known occupant profile, such as via a comparison operation of biometric data received being compared to data that is known and stored, such as a biometric measure stored in memory. The size, dimensions, motion direction, multiple phases, etc., of the biometric input data can be compared via an on-board and/or off-board processing platform to identify the accuracy of the profile data to the input biometric data. The data may be encrypted, by the transport (i.e., one or more computing devices/sensors of the transport) based on the first biometric associated with an occupant 118. The encrypting may be performed prior to receiving the first biometric or in response to receiving the first biometric and confirming the first biometric is accurate. Also, the encrypting may occur prior to or in response to identifying the first biometric is not accurate, such as a mismatch as determined by a processor with known biometric data stored in memory and associated with the intended occupant profile and the data received during a biometric capture sequence.

A second biometric 122 may be received and processed as a secondary authentication measure that is tied to a sequence of authentication operations, such as the first biometric authentication procedure. For example, the first biometric data may be a sequence of movements identified from a left hand of an occupant and detected by a sensor. The second biometric may be a similar or different set of data anticipated by the right hand of the occupant. Depending on the result of the second biometric processing event, the data may be unencrypted 124, by the transport 120, based on a verification of the second biometric, and the second biometric may be required to be a continuum of the first biometric. Once the data is unencrypted, the data may be provided 126, by the transport, to the occupant via the user interface 130. The continuum could be data that is a derivative of the original data, such as a related but different version of the original input data. In general, the relationship between the first and second biometric data is a measured continuum, and the biometric data sets (e.g., first and second biometric data) are not intended to be mutually exclusive. For instance, the first biometric may be a hand gesture sequence and the second biometric may be a second hand gesture sequence (see FIGS. IC and ID). Or, the data could be different between the first and second biometrics, such as facial recognition followed by an audible spoken command or other gesture. The continuum requirement may be a time frame and/or distance measurement between the first and second biometrics. For example, the second biometric must be received within five seconds of the first biometric and/or the second biometric must begin with 12 inches of the first biometric location. Failure to adhere to the guidelines when inputting the biometric data may yield a result that is a mismatch or failed authentication attempt.

The transport 120 may determine the received data comprises a sensitive portion and a non-sensitive portion specific to the occupant. In this scenario, the transport computing system may delete the sensitive portion of the unencrypted data 168 as the sensitive portion of the data is being provided to the user interface 130 or other output device, and the non-sensitive portion may also be deleted after a period of time associated with the second biometric has lapsed 128. For example, the non-sensitive data may not be deleted immediately after presentation to the occupant, instead, the non-sensitive data may be queued in memory in a separate memory space and maintained until the data is ready to be shared with the occupant at a later time. A period of time may be measured from when the second biometric is received at the transport as a beginning time for the duration of the non-sensitive data life. The period of time may be based on a navigation of the transport or other factors, such as a particular day, set of events and their estimated periods of time. The deletion of the non-sensitive portion after the period of time has lapsed may be performed when the second biometric is not received by the transport and after the set period of time. The biometric input of the first and/or second biometrics being received and/or confirmed and authorized may be a condition precedent to the unencrypted data being shared at all with any parties. Therefore, if the biometrics are not received, confirmed and authorized then the data may never be shared and will be deleted after the set period of time has lapsed.

Additional features may include detecting biometric data associated with the occupant as the first biometric, and detecting additional biometric data and determining whether the additional biometric data is the continuum of the first biometric data based on one or more of a time threshold, a distance threshold, a touch threshold and a relational threshold (the first biometric and second biometric are related by similar body parts such as a left hand and a right hand, and/or are related by associated functionality such as a head movement and a verbalization of the head movement that is occurring). For example, the continuum criteria may include receiving one biometric sequence and then having the other biometric sequence be received within a period of time, such as within 5 seconds of the first sequence. Another possibility is the requirement that the second biometric sequence be within a set distance of the first biometric sequence, such as a set of hand movements which are started and stopped with a certain distance of each other (e.g., 6 inches) or which are based on touch (such as the left hand moving up a steering wheel and touching a right hand which moves down the steering wheel). The example operation may also include determining one or more additional occupants are present in the transport (via a seat sensor, camera or other processor/sensor) when the received data is encrypted and providing the non-sensitive portion of the unencrypted data to a vehicle interface in the instance that there is more than one occupant in the transport. The process may also include determining, at a later time, that only the occupant is in the transport, and providing the sensitive portion of the data to the occupant then or after the occupant has exited the transport.

FIG. 1B illustrates a further example of data security processing and distribution, according to example embodiments. Referring to FIG. 1B, the configuration 150 includes a server 152 as a source of data 162, which may be requested and retrieved or forwarded to a transport 166 based upon a periodic data communication session process or other data communication procedure. The data may be received and processed by transport 166. In this example, there may be multiple different types of data, such as personal emails, text messages, phone call voice mail recordings, advertisements, news information, entertainment (e.g., music, podcasts, etc.). Any and all of those data items may have their content analyzed by a language processor application of a processor to identify words or phrases which are sensitive data 172, non-sensitive data 174, and whether to encrypt the data and credentials and whether authorization is required to unencrypt the data. In one example, the sensitive data 172 may only be shared 176 with the mobile device 170 or other computing device associated with the transport 166 when the data is contemporaneously deleted, such as right after sharing the data. Another scenario may provide the data is unencrypted and shared and then deleted after a period of time has lapsed 178, and data may only be shared with the user device 170 once it has been removed from the transport. The transport may wait a predefined period of time and/or for a distance between the device 170 and the transport 166 prior to sharing the higher risk/sensitive data 172 with the device 170.

FIG. 1C illustrates an example 180 of a hand gesture biometric being performed in the transport, according to example embodiments. In this example, any biometric input may be performed and detected by the user device 170, a computing device integrated with the transport and/or a combination thereof. This example includes a user's hands being in a particular position associated with the steering wheel to demonstrate a first biometric gesture 182 which is detected via a motion sensor and processed to compare with a known gesture or related biometric authorization procedure. This may be deemed the first biometric input of the authorization procedure.

FIG. 1D illustrates a further example 190 of a hand gesture biometric being performed in the transport, according to example embodiments. Referring to FIG. 1D, the hand gesture 192 may be a second gesture and may qualify as the second biometric input to the computing device of the transport. The gestures may be required to be continuums of one another and the criteria for determining whether the continuum y be based on time, distance and sequence thresholds. For example, the time between a first and second biometric input may be 5, 10 seconds, etc. The distance threshold may be 12-24 inches between first and second biometric inputs. Also, the second biometric may be a continuation of the first biometric input, such as a spoken phrase detected by voice recognition or movements of hands, as shown in FIGS. 1C and 1D, the first movement 182 may be a flat hand gesture from one direction to another and the second gesture 192 may be a flat hand gesture from one position to another higher position. In the event that a user's eyes are scanned, and the eyes are near the user's hands, it is probably the same user if the distance is close enough, and thus if the hand movement has a pause, the nearby continuation of movements, time and distance threshold requirements, can cause the additional biometric data to be labeled a second biometric and a qualified continuum of the first biometric. The actual physical elements in the transport being utilized, such as the steering wheel, may require the hands be at a “10” and “2” position and move towards other positions depending on the sequence that is known by the computing system application d as detected by a motion sensor. However, any combination of biometric inputs that are known and used as the basis of comparisons for authorization purposes may be selected and used to authenticate the transport occupant, such as movements, voice recognition, eye recognition, face recognition, a weight sensor, etc.

FIG. 2A illustrates a transport network diagram 200, according to example embodiments. The network comprises elements including a transport node 202 including a processor 204, as well as a transport node 202′ including a processor 204′. The transport nodes 202, 202′ communicate with one another via the processors 204, 204′, as well as other elements (not shown) including transceivers, transmitters, receivers, storage, sensors and other elements capable of providing communication. The communication between the transport nodes 202, 202′ can occur directly, via a private and/or a public network (not shown) or via other transport nodes and elements comprising one or more of a processor, memory, and software. Although depicted as single transport nodes and processors, a plurality of transport nodes and processors may be present. One or more of the applications, features, steps, solutions, etc., described and/or depicted herein may be utilized and/or provided by the instant elements.

FIG. 2B illustrates another transport network diagram 210, according to example embodiments. The network comprises elements including a transport node 202 including a processor 204, as well as a transport node 202′ including a processor 204′. The transport nodes 202, 202′ communicate with one another via the processors 204, 204′, as well as other elements (not shown) including transceivers, transmitters, receivers, storage, sensors and other elements capable of providing communication. The communication between the transport nodes 202, 202′ can occur directly, via a private and/or a public network (not shown) or via other transport nodes and elements comprising one or more of a processor, memory, and software. The processors 204, 204′ can further communicate with one or more elements 230 including sensor 212, wired device 214, wireless device 216, database 218, mobile phone 220, transport node 222, computer 224, I/O device 226 and voice application 228. The processors 204, 204′ can further communicate with elements comprising one or more of a processor, memory, and software.

Although depicted as single transport nodes, processors and elements, a plurality of transport nodes, processors and elements may be present. Information or communication can occur to and/or from any of the processors 204, 204′ and elements 230. For example, the mobile phone 220 may provide information to the processor 204, which may initiate the transport node 202 to take an action, may further provide the information or additional information to the processor 204′, which may initiate the transport node 202′ to take an action, may further provide the information or additional information to the mobile phone 220, the transport node 222, and/or the computer 224. One or more of the applications, features, steps, solutions, etc., described and/or depicted herein may be utilized and/or provided by the instant elements.

FIG. 2C illustrates yet another transport network diagram 240, according to example embodiments. The network comprises elements including a transport node 202 including a processor 204 and a non-transitory computer readable medium 242C. The processor 204 is communicably coupled to the computer readable medium 242C and elements 230 (which were depicted in FIG. 2B).

The processor 204 performs one or more of encrypting received data based on a first biometric associated with an occupant 244C, unencrypting the encrypted data, based on a verification of a second biometric, wherein the second biometric is a continuum of the first biometric 246C, and providing the unencrypted data to the occupant 248C.

FIG. 2D illustrates a further transport network diagram 250, according to example embodiments. The network comprises elements including a transport node 202 including a processor 204 and a non-transitory computer readable medium 242D. The processor 204 is communicably coupled to the computer readable medium 242D and elements 230 (which were depicted in FIG. 2B).

The processor 204 performs one or more of determining the received data comprises a sensitive portion and a non-sensitive portion specific to the occupant, and deleting the sensitive portion of the unencrypted data as the sensitive portion is being provided and the non-sensitive portion after a period of time associated with the second biometric, has lapsed 244D. The deleting the non-sensitive portion after the period of time, associated with the second biometric has lapsed, is performed when the second biometric is not received by the transport after the period of time 246D. The processor may also perform detecting biometric data associated with the occupant as the first biometric, detecting additional biometric data and determining whether the additional biometric data is the continuum of the first biometric data based on one or more of a time threshold and a distance threshold 248D, determining one or more additional occupants are present in the transport when the received data is encrypted, providing the non-sensitive portion of the unencrypted data to a vehicle interface, determining, at a later time, only the occupant is in the transport, and providing the sensitive portion of the data to the occupant 252D.

FIG. 2E illustrates a yet further transport network diagram 260, according to example embodiments. The network comprises elements including a transport node 202 including a processor 204 and a non-transitory computer readable medium 242E. The processor 204 is communicably coupled to the computer readable medium 242E and elements 230 (which were depicted in FIG. 2B). The processor 204 performs one or more of receiving a validation of the continuum from at least one component, wherein the validation comprises a blockchain consensus between a peer group consisting of the transport and the at least one component 244E, and executing a smart contract, by the transport, to record the validation and the at least one component on a blockchain based on the blockchain consensus 246E.

The processors and/or computer readable media may fully or partially reside in the interior or exterior of the transport nodes. The steps or features stored in the computer readable media may be fully or partially performed by any of the processors and/or elements in any order. Additionally, one or more steps or features may be added, omitted, combined, performed at a later time, etc.

FIG. 2F depicts a system 265 depicting electrification of one or more elements that receive and/or provide power is received and/or provided. In one embodiment a transport 266 may provide power stored in its batteries to one or more of elements including other transport(s) 268, charging station(s) 270 and electric grid(s) 272. The electric grid(s) 272 is/are coupled to one or more of the charging stations 270 which may be coupled to one or more of the transports 268 allowing distribution among one another of electricity/power received from the transport 266. The transport 266 may also interact with the other transport(s) 268, such as via V2V technology, communication over cellular, WiFi, and the like. The transport 266 may also interact wirelessly and/or in a wired manner with the charging station(s) 270, or with the electric grid(s) 272.

In one embodiment, the transport 266 is routed (or routes itself) in a safe and efficient manner to the electric grid(s) 272, the charging station(s) 270, or the other transport(s) 268. Using one or more embodiments of the instant solution, the transport 266 can provide energy to one or more of the elements depicted herein in a variety of advantageous ways. Further, the safety and efficiency of the transport may be increased, and the environment may be positively affected.

In one embodiment, the charging station 270 manages the amount of energy transferred from the transport 266 such that there is sufficient charge remaining in the transport 266 to arrive at a destination. In one embodiment, a wireless connection is used to wirelessly direct an amount of energy transfer between transports 268, where the transports may both be in motion. In one embodiment, an idle vehicle, such as an autonomous vehicle 266 (which may be autonomous) is directed to provide an amount of energy to a charging station 270 and return to the original location (for example, its original location or a different destination). In one embodiment, a mobile energy storage unit (not shown) is used to collect surplus energy from at least one other transport 268 and transfer the stored, surplus energy at a charging station 270. In one embodiment, factors determine an amount of energy to transfer to a charging station 270, such as distance, time, as well as traffic conditions, road conditions, environmental/weather conditions, the vehicle's condition (weight, etc.), an occupant(s) schedule while utilizing the vehicle, a prospective occupant(s) schedule waiting for the vehicle, etc. In one embodiment, the transport(s) 268, the charging station(s) 270 and/or the electric grid(s) 272 can provide energy to the transport 266.

In one embodiment, the solutions described and depicted herein can be utilized to determine load effects on the transport and/or the system, to provide energy to the transport and/or the system based on future needs and/or priorities, and. provide intelligence between an apparatus containing a module and a vehicle allowing the processor of the apparatus to wireless communicate with a vehicle regarding an amount of energy store in a battery on the vehicle. In one embodiment, the solutions can also be utilized to provide charge to a location from a transport based on factors such as the temperature at the location, the cost of the energy and the power level at the location. In one embodiment, the solutions can also be utilized to manage an amount of energy remaining in a transport after a portion of charge has been transferred to a charging station. In one embodiment, the solutions can also be utilized to notify a vehicle to provide an amount of energy from batteries on the transport wherein the amount of energy to transfer is based on the distance of the transport to a module to receive the energy. In one embodiment, the solutions can also be utilized to use a mobile energy storage unit that uses a determined path to travel to transports that have excess energy and deposit the stored energy into the electric grid. In one embodiment, the solutions can also be utilized to determine a priority of the transport's determination of the need to provide energy to grid, and the priority of a current need of the transport, such as the priority of a passenger, or upcoming passenger, or current cargo, or upcoming cargo. In one embodiment, the solutions can also be utilized to determine that when a vehicle is idle, the vehicle decides to maneuver to a location to discharge excess energy to the energy grid, then return to the previous location. In one embodiment, the solutions can also be utilized to determine an amount of energy needed by a transport to provide another transport with needed energy via transport to transport energy transfer based on one or more conditions such as weather, traffic, road conditions, car conditions, and occupants and/or goods in another transport, and instruct the transport to route to another transport and provide the energy. In one embodiment, the solutions can also be utilized to transfer energy from one vehicle in motion to another vehicle in motion. In one embodiment, the solutions can also be utilized to retrieve energy by a transport based on an expended energy by the transport to reach a meeting location with another transport, provide a service, and an estimated expended energy to return to an original location. In one embodiment, the solutions can also be utilized to provide a remaining distance needed to a charging station, and the charging station to determine an amount of energy to be retrieved from the transport wherein the amount of charge remaining is based on the remaining distance. In one embodiment, the solutions can also be utilized to manage a transport that is concurrently charged by more than one point at the same time, such as both a charging station via a wired connection and another transport via a wireless connection. In one embodiment, the solutions can also be utilized to apply a priority to the dispensing of energy to transports wherein a priority is given to those transports that will provide a portion of their stored charge to another entity such as an electric grid, a residence, and the like. Further, the instant solution as described and depicted with respect to FIG. 2F can be utilized in this and other networks and/or systems.

FIG. 2G is a diagram showing interconnections between different elements 275. The instant solution may be stored and/or executed entirely or partially on and/or by one or more computing devices 278′, 279′, 281′, 282′, 283′, 284′, 276′, 285′, 287 and 277′ associated with various entities, all coupled and in communication with a network 286. A database 287 is communicably coupled to the network and allows for the storage and retrieval of data. In one embodiment, the database is an immutable blockchain ledger. One or more of the various entities may be a transport 276, one or more service provider 279, one or more public buildings 281, one or more traffic infrastructure 282, one or more residential dwellings 283, an electric grid/charging station 284, a microphone 285, and/or another transport 277. Other entities and/or devices, such as one or more private users using a smartphone 278, a laptop 280, and/or a wearable device may also interwork with the instant solution. The smartphone 278, laptop 280, the microphone 285, and other devices may be connected to one or more of the connected computing devices 278′, 279′, 281′, 282′, 283′, 284′, 276′, 285′, 287, and 277′. The one or more public buildings 281 may include various agencies. The one or more public buildings 281 may utilize a computing device 281′. The one or more public buildings 281 may utilize a computing device 281′. The one or more service provider 279 may include a dealership, a tow truck service, a collision center or other repair shop. The one or more service provider 279 may utilize a computing apparatus 279′. These various computer devices may be directly and/or communicably coupled to one another such as via wired networks, wireless networks, blockchain networks, and the like. The microphone 285 may be utilized as a virtual assistant, in one embodiment. In one embodiment, the one or more traffic infrastructure 282 may include one or more traffic signals, one or more sensors including one or more cameras, vehicle speed sensors or traffic sensors, and/or other traffic infrastructure. The one or more traffic infrastructure 282 may utilize a computing device 282′.

In one embodiment, a transport 277/276 is capable of transporting a person, an object, a permanently or temporarily affixed apparatus, and the like. In one embodiment, the transport 277 may communicate with transport 276 via V2V communication, through the computers associated with each transport 276′ and 277′ and may be referred to as a transport, vehicle, automobile, and the like. The transport 277/276 may be a self-propelled wheeled conveyance, such as a car, a sports utility vehicle, a truck, a bus, a van, or other motor or battery-driven or fuel cell-driven transport. For example, transport 277/276 may be an electric vehicle, a hybrid vehicle, a hydrogen fuel cell vehicle, a plug-in hybrid vehicle, or any other type of vehicle that has a fuel cell stack, a motor, and/or a generator. Other examples of vehicles include bicycles, scooters, trains, planes, or boats, and any other form of conveyance that is capable of transportation. The transport 277/276 may be semi-autonomous or autonomous. For example, transport 277/276 may be self-maneuvering and navigate without human input. An autonomous vehicle may have and use one or more sensors and/or a navigation unit to drive autonomously.

In one embodiment, the solutions described and depicted herein can be utilized to determine a one-time access to a transport via consensus of blockchain. In one embodiment, the solutions can also be utilized to perform profile validation before allowing an occupant to use a transport. In one embodiment, the solutions can also be utilized to indicate to have the transport indicate (visually, but also verbally in another embodiment, etc.) on or from the transport for an action the user needs to perform (that could be pre-recorded) and verify that it is the correct action. In one embodiment, the solutions can also be utilized to provide an ability to for a transport to determine, based on the risk level associated with data and driving environment, how to bifurcate the data and distribute a portion of the bifurcated data, with lower risk level during a safe driving environment, to the occupant, and later distributing a remaining portion of the bifurcated data, with a higher risk level, to the occupant after the occupant has departed the transport. In one embodiment, the solutions can also be utilized to handle the transfer of a vehicle across boundaries (such as a country/state/etc.) through the use of blockchain and/or smart contracts and apply the rules of the new area to the vehicle.

In one embodiment, the solutions can also be utilized to allow a transport to continue to operate outside a boundary when a consensus is reached by the transport based on the operation of the transport and characteristics of an occupant of the transport. In one embodiment, the solutions can also be utilized to analyze the available data upload/download speed of a transport, size of the file and speed/direction the transport is traveling, to determine the distance needed to complete a data upload/download and assign a secure area boundary for the data upload/download to be executed. In one embodiment, the solutions can also be utilized to perform a normally dangerous maneuver in a safe manner, such as when the system determines that an exit is upcoming and when the transport is seemingly not prepared to exit (e.g. in the incorrect lane or traveling at a speed that is not conducive to making the upcoming exit) and instruct the subject transport as well as other proximate transports to allow the subject transport to exit in a safe manner. In one embodiment, the solutions can also be utilized to use one or more vehicles to validate diagnostics of another transport while both the one or more vehicles and the other transport are in motion.

In one embodiment, the solutions can also be utilized to detect lane usage at a location and time of day to either inform an occupant of a transport or direct the transport to recommend or not recommend a lane change. In one embodiment, the solutions can also be utilized to eliminate the need to send information through the mail and the need for a driver/occupant to respond by making a payment (e.g., a check or money order) through the mail or in person. In one embodiment, the solutions can also be utilized to provide a service to an occupant of a transport, wherein the service provided is based on a subscription, and wherein the permission is acquired from other transports connected to the profile of the occupant. In one embodiment, the solutions can also be utilized to record changes in the condition of a rented object. In one embodiment, the solutions can also be utilized to seek a blockchain consensus from other transports that are in proximity to a damaged transport. In one embodiment, the solutions can also be utilized to receive media, from a server such as an insurance entity server, from the transport computer, which may be related to an accident. The server accesses one or more media files to access the damage to the transport and stores the damage assessment onto a blockchain. In one embodiment, the solutions can also be utilized to obtain a consensus to determine the severity of an event from a number of devices over various times prior to the event related to a transport.

In one embodiment, the solutions can also be utilized to solve a problem with a lack of video evidence for transport-related accidents. Detailing the querying of media, by the transport involved in the accident, related to the accident from other transports that may have been proximate to the accident. In one embodiment, the solutions can also be utilized to utilize transports and other devices (for example, a pedestrian's cell phone, a streetlight camera, etc.) to record specific portions of a damaged transport.

In one embodiment, the solutions can also be utilized to warn an occupant when a transport is navigating toward a dangerous area and/or event, allowing for a transport to notify occupants or a central controller of a potentially dangerous area on or near the current transport route. In one embodiment, the solutions can also be utilized to detect when a transport traveling at a high rate of speed, at least one other transport is used to assist in slowing down the transport in a manner that minimally affects traffic. In one embodiment, the solutions can also be utilized to identify a dangerous driving situation where media is captured by the vehicle involved in the dangerous driving situation. A geofence is established based on the distance of the dangerous driving situation, and additional media is captured by at least one other vehicle within the established geofence. In one embodiment, the solutions can also be utilized to send a notification to one or more occupants of a transport that that transport is approaching a traffic control marking on a road, then if a transport crosses a marking, receiving indications of poor driving from other, nearby transports. In one embodiment, the solutions can also be utilized to make a transport partially inoperable by (in certain embodiments), limiting speed, limiting the ability to be near another vehicle, limiting speed to a maximum, and allowing only a given number of miles allowed per time period.

In one embodiment, the solutions can also be utilized to overcome a need for reliance on software updates to correct issues with a transport when the transport is not being operated correctly. Through the observation of other transports on a route, a server will receive data from potentially multiple other transports observing an unsafe or incorrect operation of a transport. Through analysis, these observations may result in a notification to the transport when the data suggest an unsafe or incorrect operation. In one embodiment, the solutions can also be utilized to provide notification between a transport and a potentially dangerous situation involving a person external to the transport. In one embodiment, the solutions can also be utilized to send data to a server by devices either associated with an accident with a transport, or devices proximate to the accident. Based on the severity of the accident or near accident, the server notifies the senders of the data. In one embodiment, the solutions can also be utilized to provide recommendations for operating a transport to either a driver or occupant of a transport based on the analysis of data. In one embodiment, the solutions can also be utilized to establish a geo-fence associated with a physical structure and determining payment responsibility to the transport. In one embodiment, the solutions can also be utilized to coordinate the ability to drop off a vehicle at a location using both the current state at the location, and a proposed future state using navigation destinations of other vehicles. In one embodiment, the solutions can also be utilized to coordinate the ability to automatically arrange for the drop off of a vehicle at a location such as a transport rental entity.

In one embodiment, the solutions can also be utilized to move transport to another location based on a user's event. More particularly, the system tracks a user's device, and modifies the transport to be moved proximate to the user upon the conclusion of the original event, or a modified event. In one embodiment, the solutions can also be utilized to allow for the validation of available locations within an area through the existing transports within the area. The approximate time when a location may be vacated is also determined based on verifications from the existing transports. In one embodiment, the solutions can also be utilized to move a transport to closer parking spaces as one becomes available and the elapsed time since initially parking is less than the average time of the event. Furthermore, moving the transport to a final parking space when the event is completed or according to a location of a device associated with at least one occupant of the transport. In one embodiment, the solutions can also be utilized to plan for the parking prior to the upcoming crowd. The system interacts with the transport to offer some services at a less than full price and/or guide the transport to alternative parking locations based on a priority of the transport, increasing optimization of the parking situation before arriving.

In one embodiment, the solutions can also be utilized to sell fractional ownership in transports or in determining pricing and availability in ride-sharing applications. In one embodiment, the solutions can also be utilized to provide accurate and timely reports of dealership sales activities well beyond what is currently available. In one embodiment, the solutions can also be utilized to allow a dealership to request an asset over the blockchain. By using the blockchain, a consensus is obtained before any asset is moved. Additionally, the process is automated, and payment may be initiated over the blockchain. In one embodiment, the solutions can also be utilized to arrange agreements that are made with multiple entities (such as service centers) wherein a consensus is acquired, and an action performed (such as diagnostics). In one embodiment, the solutions can also be utilized to associate digital keys with multiple users. A first user may be the operator of the transport, and a second user is the responsible party for the transport. These keys are authorized by a server where the proximity of the keys are validated against the location of a service provider. In one embodiment, the solutions can also be utilized to determine a needed service on a transport destination. One or more service locations are located that are able to provide the needed service that is both within an area on route to the destination and has availability to perform the service. The navigation of the transport is updated with the determined service location. A smart contract is identified that contains a compensation value for the service, and a blockchain transaction is stored in a distributed ledger for the transaction.

In one embodiment, the solutions can also be utilized to interfacing a service provider transport with a profile of an occupant of a transport to determine services and goods which may be of interest to occupants in a transport. These services and goods are determined by an occupant's history and/or preferences. The transport then receives offers from the service provider transport and, in another embodiment, meets the transport to provide the service/good. In one embodiment, the solutions can also be utilized to detect a transport within a range and send a service offer to the transport (such as a maintenance offer, a product offer, or the like). An agreement is made between the system and the transport, and a service provider is selected by the system to provide the agreement. In one embodiment, the solutions can also be utilized to assign one or more transports as a roadway manager, where the roadway manager assists in the control of traffic. The roadway manager may generate a roadway indicator (such as lights, displays, sounds) to assist in the flow of traffic. In one embodiment, the solutions can also be utilized to alert a driver of a transport by a device, wherein the device may be the traffic light or near an intersection. The alert is sent upon an event, such as when a light turns green and the transport in the front of a list of transports does not move.

FIG. 2H is another block diagram showing interconnections between different elements in one example 290. A transport 276 is presented and includes ECUs 295, 296, and a Head Unit (otherwise known as an Infotainment System) 297. An Electrical Control Unit (ECU) is an embedded system in automotive electronics controlling one or more of the electrical systems or subsystems in a transport. ECUs may include but are not limited to the management of a transport's engine, brake system, gearbox system, door locks, dashboard, airbag system, infotainment system, electronic differential, and active suspension. ECUs are connected to the transport's Controller Area Network (CAN) bus 294. The ECUs may also communicate with a transport computer 298 via the CAN bus 294. The transport's processors/sensors (such as the transport computer) 298 can communicate with external elements, such as a server 293 via a network 292 (such as the Internet). Each ECU 295, 296 and Head Unit 297 may contain its own security policy. The security policy defines permissible processes that are able to be executed in the proper context. In one embodiment, the security policy may be partially or entirely provided in the transport computer 298.

ECUs 295, 296 and Head Unit 297 may each include a custom security functionality element 299 defining authorized processes and contexts within which those processes are permitted to run. Context-based authorization to determine validity if a process is able to be executed allows ECUs to maintain secure operation and prevent unauthorized access from elements such as the transport's Controller Area Network (CAN Bus). When an ECU encounters a process that is unauthorized, that ECU can block the process from operating. Automotive ECUs can use different contexts to determine whether a process is operating within its permitted bounds, such as proximity contexts such as nearby objects, distance to approaching objects, speed, and trajectory relative to other moving objects, operational contexts such as is the transport moving or parked, the transport's current speed, the transmission state, user-related contexts such as devices connected to the transport via protocols such as Bluetooth, WiFi, and the like, use of the infotainment, cruise control, parking assist, driving assist, location-based contexts, and/or other contexts.

In one embodiment, the solutions described and depicted herein can be utilized to make a transport partially inoperable by (in certain embodiments), limiting speed, limiting the ability to be near another vehicle, limiting speed to a maximum, and allowing only a given numbers of miles allowed per time period. In one embodiment, the solutions can also be utilized to use a blockchain to facilitate exchange of vehicle possession wherein data is sent to a server by devices either associated with an accident with a transport, or devices proximate to the accident. Based on the severity of the accident or near accident, the server notifies the senders of the data. In one embodiment, the solutions can also be utilized to help the transport to avoid accidents, such as when the transport is involved in an accident by a server that queries other transports that are proximate to the accident. The server seeks to obtain data from the other transports, allowing the server to gain an understanding of the nature of the accident from multiple vantage points. In one embodiment, the solutions can also be utilized to determine that sounds from a transport are atypical and transmit data related to the sounds as well as a possible source location to a server wherein the server can determine possible causes and avoid a potentially dangerous situation. In one embodiment, the solutions can also be utilized to establish a location boundary via the system when a transport is involved in an accident. This boundary is based on decibels associated with the accident. Multimedia content for a device within the boundary is obtained to assist in further understanding the scenario of the accident. In one embodiment, the solutions can also be utilized to associate a vehicle with an accident, then capture media obtained by devices proximate to the location of the accident. The captured media is saved as a media segment. The media segment is sent to another computing device which builds a sound profile of the accident. This sound profile will assist in understanding more details surrounding the accident.

In one embodiment, the solutions can also be utilized to utilize sensors to record audio, video, motion, etc. to record an area where a potential event has occurred, such as if a transport comes in contact or may come in contact with another transport (while moving or parked), the system captures data from the sensors which may reside on one or more of the transports and/or on fixed or mobile objects. In one embodiment, the solutions can also be utilized to determine that a transport has been damaged by using sensor data to identify a new condition of the transport during a transport event and comparing the condition to a transport condition profile, making it possible to safely and securely capture critical data from a transport that is about to be engaged in a detrimental event.

In one embodiment, the solutions can also be utilized to warn occupants of a transport when the transport, via one or more sensors, has determined that it is approaching or going down a one-way road the incorrect way. The transport has sensors/cameras/maps interacting with the system of the current embodiment. The system knows the geographic location of one way streets. The system may audibly inform the occupants, “Approaching a one way street”, for example. In one embodiment, the solutions can also be utilized to allow the transport to get paid allowing autonomous vehicle owners to monetize the data their vehicle sensors collect and store creating an incentive for vehicle owners to share their data and provide entities with additional data through which to improve the performance of future vehicles, provide services to the vehicle owners, etc.

In one embodiment, the solutions can also be utilized to either increase or decrease a vehicle's features according to the action of the vehicle over a period of time. In one embodiment, the solutions can also be utilized to assign a fractional ownership to a transport. Sensor data related to one or more transports and a device proximate to the transport are used to determine a condition of the transport. The fractional ownership of the transport is determined based on the condition and a new responsibility of the transport is provided. In one embodiment, the solutions can also be utilized to provide data to a replacement/upfitting component, wherein the data attempts to subvert an authorized functionality of the replacement/upfitting component, and responsive to a non-subversion of the authorized functionality, permitting, by the component, use of the authorized functionality of the replacement/upfitting component.

In one embodiment, the solutions can also be utilized to provide individuals the ability to ensure that an occupant should be in a transport and for that occupant to reach a particular destination. Further, the system ensures a driver (if a non-autonomous transport) and/or other occupants are authorized to interact with the occupant. Also, pickups, drop-offs and location are noted. All of the above are stored in an immutable fashion on a blockchain. In one embodiment, the solutions can also be utilized to determine characteristics of a driver via an analysis of driving style and other elements to take action in the event that the driver is not driving in a normal manner, such as a manner in which the driver has previously driven in a particular condition, for example during the day, at night, in the rain, in the snow, etc. Further, the attributes of the transport are also taken into account. Attributes consist of weather, whether the headlights are on, whether navigation is being used, a HUD is being used, volume of media being played, etc. In one embodiment, the solutions can also be utilized to notify occupants in a transport of a dangerous situation when items inside the transport signify that the occupants may not be aware of the dangerous situation.

In one embodiment, the solutions can also be utilized to mount calibration devices on a rig that is fixed to a vehicle wherein the various sensors on the transport are able to automatically self-adjust based on what should be detected by the calibration devices as compared to what is actually detected. In one embodiment, the solutions can also be utilized to use a blockchain to require consensus from a plurality of service centers when a transport needing service sends malfunction information allowing remote diagnostic functionality wherein a consensus is required from other service centers on what a severity threshold is for the data. Once the consensus is received, the service center may send the malfunction security level to the blockchain to be stored. In one embodiment, the solutions can also be utilized to determine a difference in sensor data external to the transport and the transport's own sensor data. The transport requests, from a server, a software to rectify the issue. In one embodiment, the solutions can also be utilized to allow for the messaging of transports that are either nearby, or in the area, when an event occurs (e.g. a collision).

Referring to FIG. 2I, an operating environment 290A for a connected transport is illustrated according to some embodiments. As depicted, the transport 276 includes a Controller Area Network (CAN Bus) 291A connecting elements (292A-299A) of the transport. Other elements may be connected to the CAN bus and are not depicted herein. The depicted elements connected to the CAN bus include a sensor set 292A, Electronic Control Units 293A, autonomous features or Advanced Driver Assistance Systems (ADAS) 294A, and the navigation system 295A. In some embodiments, the transport 276 includes a processor 296A, a memory 297A, a communication unit 298A, and an electronic display 299A.

The processor 296A includes an arithmetic logic unit, a microprocessor, a general-purpose controller, and/or a similar processor array to perform computations and provide electronic display signals to a display unit 299A. The processor 296A processes data signals and may include various computing architectures including a complex instruction set computer (CISC) architecture, a reduced instruction set computer (RISC) architecture, or an architecture implementing a combination of instruction sets. The transport 276 may include one or more processors 296A. Other processors, operating systems, sensors, displays, and physical configurations may be possible but are not depicted.

Memory 297A is a non-transitory memory storing instructions or data that may be accessed and executed by the processor 296A. The instructions and/or data may include code to perform the techniques described herein. The memory 297A may be a dynamic random access memory (DRAM) device, a static random access memory (SRAM) device, flash memory, or some other memory device. In some embodiments, the memory 297A also may include non-volatile memory or a similar permanent storage device and media which may include a hard disk drive, a floppy disk drive, a CD-ROM device, a DVD-ROM device, a DVD-RAM device, a DVD-RW device, a flash memory device, or some other mass storage device for storing information on a permanent basis. A portion of the memory 297A may be reserved for use as a buffer or virtual random access memory (virtual RAM). The transport 276 may include one or more memories 297A without deviating from the current implementation.

The memory 297A of the transport 276 may store one or more of the following types of data: navigation route data 295A, and autonomous features data 294A. In some embodiments, the memory 297A stores data that may be necessary for the navigation application 295A to provide the functions.

The navigation system 295A may describe at least one navigation route including a start point and an endpoint. In some embodiments, the navigation system 295A of the transport 276 receives a request from a user for navigation routes wherein the request includes a starting point and an ending point. The navigation system 295A may query a real-time data server 293 (via a network 292), such as a server that provides driving directions, for navigation route data corresponding to navigation routes including the start point and the endpoint. The real-time data server 293 transmits the navigation route data to the transport 276 via a wireless network 292 and the communication system 298A stores the navigation data 295A in the memory 297A of the transport 276.

The ECU 293A controls the operation of many of the systems of the transport 276, including the ADAS systems 294A. The ECU 293A may, responsive to instructions received from the navigation system 295A, deactivate any unsafe and/or unselected autonomous features for the duration of a journey controlled by the ADAS systems 294A. In this way, the navigation system 295A may control whether ADAS systems 294A are activated or enabled so that they may be activated for a given navigation route.

The sensor set 292A may include any sensors in the transport 276 generating sensor data. For example, the sensor set 292A may include short-range sensors and long-range sensors. In some embodiments, the sensor set 292A of the transport 276 may include one or more of the following vehicle sensors: a camera; a LIDAR sensor; an ultrasonic sensor; an automobile engine sensor; a radar sensor; a laser altimeter; a manifold absolute pressure sensor; an infrared detector; a motion detector; a thermostat; a sound detector, a carbon monoxide sensor; a carbon dioxide sensor; an oxygen sensor; a mass airflow sensor; an engine coolant temperature sensor; a throttle position sensor; a crankshaft position sensor; a valve timer; an air-fuel ratio meter; a blind spot meter; a curb feeler; a defect detector; a Hall effect sensor, a parking sensor; a radar gun; a speedometer; a speed sensor; a tire-pressure monitoring sensor; a torque sensor; a transmission fluid temperature sensor; a turbine speed sensor (TSS); a variable reluctance sensor; a vehicle speed sensor (VSS); a water sensor; a wheel speed sensor; a GPS sensor, a mapping functionality, and any other type of automotive sensor. The navigation system 295A may store the sensor data in the memory 297A.

The communication unit 298A transmits and receives data to and from the network 292 or to another communication channel. In some embodiments, the communication unit 298A may include a DSRC transceiver, a DSRC receiver and other hardware or software necessary to make the transport 276 a DSRC-equipped device.

The transport 276 may interact with other transports 277 via Vehicle to Vehicle (V2V) technology. V2V communication includes sensing radar information corresponding to relative distances to external objects, receiving GPS information of the transports, setting areas as areas where the other transports 277 are located based on the sensed radar information, calculating probabilities that the GPS information of the object vehicles will be located at the set areas, and identifying transports and/or objects corresponding to the radar information and the GPS information of the object vehicles based on the calculated probabilities, in one embodiment.

In one embodiment, the solutions described and depicted herein can be utilized to Manage emergency scenarios and transport features when a transport is determined to be entering an area without network access. In one embodiment, the solutions can also be utilized to manage and provide features in a transport (such as audio, video, navigation, etc.) without network connection. In one embodiment, the solutions can also be utilized to determine when a profile of a person in proximity to the transport matches profile attributes of a profile of at least one occupant in the transport. A notification is sent from the transport to establish communication.

In one embodiment, the solutions can also be utilized to analyze the availability of occupants in respective transports that are available for a voice communication based on an amount of time remaining in the transport and context of the communication to be performed. In one embodiment, the solutions can also be utilized to determine two levels of threat of roadway obstruction and receiving a gesture that may indicate that the obstruction is not rising to an alert above a threshold, and proceeding, by the transport along the roadway. In one embodiment, the solutions can also be utilized to delete sensitive data from a transport when the transport has had damage such that it is rendered unable to be used.

In one embodiment, the solutions can also be utilized to verify that the customer data to be removed has truly been removed from all of the required locations within the enterprise demonstrating GDPR compliance. In one embodiment, the solutions can also be utilized to provide consideration from one transport to another transport in exchange for data related to safety, important notifications, etc. to enhance the autonomous capabilities of the lower level autonomous vehicle. In one embodiment, the solutions can also be utilized to provide an ability for a transport to receive data based on a first biometric associated with an occupant. Then the transport unencrypts the encrypted data based on a verification of a second biometric, wherein the second biometric is a continuum of the first biometric. The transport provides the unencrypted data to the occupant when only the occupant is able to receive the unencrypted data and deletes a sensitive portion of the unencrypted data as the sensitive portion is being provided and a non-sensitive portion after a period of time associated with the biometric elapses. In one embodiment, the solutions can also be utilized to provide an ability for a transport to validate an individual based on a weight and grip pressure applied to the steering wheel of the transport. In one embodiment, the solutions can also be utilized to provide a feature to a car that exists but is not currently enabled presenting features to an occupant of the automobile that reflects the occupant's characteristics.

In one embodiment, the solutions can also be utilized to allow for the modification of a transport, particularly the interior of the transport as well as the exterior of the transport to reflect, and assist at least one occupant, in one embodiment. In another embodiment, recreating an occupant's work and/or home environment is disclosed. The system may attempt to “recreate” the user's work/home environment while the user is in the transport if it determines that the user is in “work mode” or “home mode”. All data related to the interior and exterior of the transport as well as the various occupants utilizing the transport are stored on a blockchain and executed via smart contracts. In one embodiment, the solutions can also be utilized to detect occupant gestures to assist in communicating with nearby transports wherein the transport may maneuver accordingly. In one embodiment, the solutions can also be utilized to provide the ability for a transport to detect intended gestures using a gesture definition datastore. In one embodiment, the solutions can also be utilized to provide an ability for a transport to take various actions based on a gait and a gesture of a user. In one embodiment, the solutions can also be utilized to ensure that a driver of a transport that is currently engaged in various operations (for example, driving while talking with navigation on, etc.) does not exceed an unsafe number of operations before being permitted to gesture.

In one embodiment, the solutions can also be utilized to assign a status to each occupant in a transport and validating a gesture from an occupant based on the occupant's status. In one embodiment, the solutions can also be utilized to collect details of sound related to a collision (in what location, in what direction, rising or falling, from what device, data associated with the device such as type, manufacturer, owner, as well as the number of contemporaneous sounds, and the times the sounds were emanated, etc.) and provide to the system where analysis of the data assists in determining details regarding the collision. In one embodiment, the solutions can also be utilized to provide a determination that a transport is unsafe to operate. The transport includes multiple components that interoperate to control the transport, and each component is associated with a separate component key. A cryptographic key is sent to the transport to decrease transport functionality. In response to receiving the cryptographic key, the transport disables one or more of the component keys. Disabling the one or more component keys results in one or more of limiting the transport to not move greater than a given speed, limiting the transport to not come closer than a distance to another transport, and limiting the transport to not travel greater than a threshold distance.

In one embodiment, the solutions can also be utilized to provide an indication from one specific transport (that is about to vacate a location) to another specific transport (that is seeking to occupy a location), a blockchain is used to perform authentication and coordination. In one embodiment, the solutions can also be utilized to determine a fractional responsibility for a transport. Such as the case where multiple people own a single transport, and the use of the transport, which may change over a period of time, is used by the system to update the fractional ownership. Other embodiments will be included in the application including a minimal ownership of a transport based on not the use of the transport, but the availability of the transport, and the determination of the driver of the transport as well as others.

In one embodiment, the solutions can also be utilized to permit in a transport a user to his/her subscriptions with a closed group of people such as family members or friends. For example, a user might want to share a membership, the embodiment stores sharing transactions in a blockchain. When the subscribed materials are requested by a user, who is not a primary subscriber, a blockchain node (i.e., a transport) can verify that a person requesting a service is an authorized person with whom the subscriber has shared the profile. In one embodiment, the solutions can also be utilized to allow a person to utilize supplemental transport(s) to arrive at an intended destination. A functional relationship value (e.g. value that indicates the various parameters and their importance in determining what type of alternate transport to utilize) is used in determining the supplemental transport. In one embodiment, the solutions can also be utilized to allow the occupants in an accident to have access to other transports to continue to their initial destination.

In one embodiment, the solutions can also be utilized to propagate a software/firmware upload to a first subset of transports. This first set of transports test the update, and when the test is successful, the update is propagated to a further set of transports. In one embodiment, the solutions can also be utilized to propagate software/firmware updates to vehicles from a master transport where the update is propagated through the network of vehicles from a first subset, then a larger subset, etc. A portion of the update may be first sent, then the remaining portion sent from the same or another vehicle. In one embodiment, the solutions can also be utilized to provide an update for a transport's computer to the transport and a transport operator's/occupant's device. The update is maybe authorized by all drivers and/or all occupants. The software update is provided to the vehicle and the device(s). The user doesn't have to do anything but go proximate to the vehicle and the functionality automatically occurs. A notification is sent to the device(s) indicating that the software update is completed. In one embodiment, the solutions can also be utilized to validate that an OTA software update is performed by a qualified technician and generation, by the one or more transport components, of a status related to: an originator of the validation code, a procedure for wirelessly receiving the software update, information contained in the software update, and results of the validation.

In one embodiment, the solutions can also be utilized to provide the ability to parse a software update located in a first component by a second component. Then verifying the first portion of critical updates and a second portion of non-critical updates, assigning the verified first portion to one process in the transport, running the verified first portion with the one process for a period of time, and responsive to positive results based on the period of time, running the verified first portion with other processes after the period of time. In one embodiment, the solutions can also be utilized to provide a selection of services to an occupant where the services are based on a profile of an occupant of the transport, and a shared profile which is shared with the profile of the occupant. In one embodiment, the solutions can also be utilized to store user profile data in a blockchain and intelligently present offers and recommendations to a user based on the user's automatically gathered history of purchases and preferences acquired from the user profile on the blockchain.

FIG. 3A illustrates a flow diagram 300, according to example embodiments. Referring to FIG. 3A, the example process includes a processor configured to encrypt received data based on a first biometric associated with an occupant 302, unencrypt the encrypted data, based on a verification of a second biometric, wherein the second biometric is a continuum of the first biometric 304, and provide the unencrypted data to the occupant 306.

FIG. 3B illustrates another flow diagram 320, according to example embodiments. Referring to FIG. 3B, a processor is further configured to perform one or more of determine the received data comprises a sensitive portion and a non-sensitive portion specific to the occupant, and delete the sensitive portion of the unencrypted data as the sensitive portion is being provided and the non-sensitive portion after a period of time, associated with the second biometric, has lapsed 322, wherein the deletion of the non-sensitive portion after the period of time, associated with the second biometric has lapsed, is performed when the second biometric is not received by the transport after the period of time 324, detect biometric data associated with the occupant as the first biometric, detect additional biometric data, determine whether the additional biometric data is the continuum of the first biometric data based on one or more of a time threshold and a distance threshold 326, determine one or more additional occupants are present in the transport when the received data is encrypted, provide the non-sensitive portion of the unencrypted data to a vehicle interface, determine, at a later time, only the occupant is in the transport, and provide the sensitive portion of the data to the occupant 328.

FIG. 3C illustrates yet another flow diagram 340, according to example embodiments. Referring to FIG. 3C, the transport further includes a receiver configured to perform one or more of receive a validation of the continuum from at least one component, wherein the validation comprises a blockchain consensus between a peer group consisting of the transport and the at least one component 342, and wherein the processor is further configured to execute a smart contract, by the transport, to record the validation and the at least one component on a blockchain based on the blockchain consensus 344.

In one example embodiment, a transport may access data requested by an occupant of the transport, determine characteristics of the data based on a risk level associated with the data and a driving environment of the transport. The transport bifurcates the data and distributes a portion of the bifurcated data with a lower risk level during a safe driving environment to the occupant and then distributes a remaining portion of the bifurcated data with a higher risk level to the occupant after the occupant has departed the transport.

In another embodiment, the transport dynamically requests data (without input from an occupant). In yet another embodiment, one or more occupants may request the data from the transport. This request could be verbal, a hand sign, interaction with a head unit, or interaction with other hardware in the transport. If data is meant for only one occupant, the data may be diverted to their device instead of share with others in the transport. The other occupants may not be permitted to access the data due to the nature of the communication or risk level associated with sharing the data. Information that is being provided or streamed to the vehicle may be delivered to each occupant differently. For example, the driver may not receive any data, the adult passengers may have full access, and the children (i.e., minors) may receive a modified version. Policy guides may be used to access the data with dynamically modified policies based on different attributes. Policy guides can be stored in distributed locations and/or on the vehicle. If data is from the U.S., then the date policies may be bound by U.S. laws. For example, in the U.S. no permission is needed to access your spouse's data. However, such rules are different in Europe. In another embodiment, medical information, such as for access to e911 may be provided. For example, driving in Canada verses driving in the US, there may be different laws, based on location, and access may be compiled based on attributes, such as location, risk level, etc. In a further embodiment, access may be provided based on who sent the encryption keys, what needs to be shared, for how long data needs to be shared. In another embodiment the transport could utilize the information and automatically send an alert when a crash is detected to appropriate parties (i.e., ambulance).

FIG. 4 illustrates a machine learning transport network diagram 400, according to example embodiments. The network 400 includes a transport node 402 that interfaces with a machine learning subsystem 406. The transport node includes one or more sensors 404.

The machine learning subsystem 406 contains a learning model 408, which is a mathematical artifact created by a machine learning training system 410 that generates predictions by finding patterns in one or more training data sets. In some embodiments, the machine learning subsystem 406 resides in the transport node 402. In other embodiments, the machine learning subsystem 406 resides outside of the transport node 402.

The transport node 402 sends data from the one or more sensors 404 to the machine learning subsystem 406. The machine learning subsystem 406 provides the one or more sensor 404 data to the learning model 408, which returns one or more predictions. The machine learning subsystem 406 sends one or more instructions to the transport node 402 based on the predictions from the learning model 408.

In a further embodiment, the transport node 402 may send the one or more sensor 404 data to the machine learning training system 410. In yet another embodiment, the machine learning subsystem 406 may sent the sensor 404 data to the machine learning subsystem 410. One or more of the applications, features, steps, solutions, etc., described and/or depicted herein may utilize the machine learning network 400 as described herein.

Additional example embodiments provides a manner in which to determine what type of data should be deleted and the time frame associated with deleting the data. This data can be stored in any portion of a transport, an ECU, a HU, memory, etc. In one embodiment, a transport encrypts received data based on a first biometric associated with an occupant. Then the transport unencrypts the encrypted data based on a verification of a second biometric, and the second biometric is a continuum of the first biometric. The transport may provide the unencrypted data to the occupant when only the occupant is able to receive the unencrypted data and delete a sensitive portion of the unencrypted data as the sensitive portion is being provided and a non-sensitive portion after a period of time associated with the biometric elapses. In another embodiment, the deleting of the non-sensitive portion after the period of time associated with the biometric elapses comprises not receiving, by the transport, the continuum of the second biometric after a period of time.

In yet another embodiment, personal data (i.e., account numbers, log-in data, biometrics, etc.) is immediately deleted upon use/verification by the transport. In a further embodiment, certain personal data and/or non-personal data can be stored for a longer period of time. For example, a user may be located in their personal transport as compared to a rideshare transport and may desire that some of this data be retained and not immediately deleted. In yet a further embodiment, prior to the deletion of the data, some or all of the data can be stored on a server. The server can compare the stored data to previously stored data. The stored data and the previously stored data are related based on one or more of: being acquired from a same or similar location, being acquired from a same or similar condition (e.g., environmental, road, traffic, driver, passenger, etc.), and/or a same or similar action has occurred. In another embodiment, the encryption may be based on key/pairs, data hiding and/or encapsulation. Encapsulation may be wrapping the implementation of data member and methods inside a class. Data hiding may be used to protect the members of a class from an illegal or unauthorized access. The secure wireless connection between a server, a transport and/or a mobile device could be BLUETOOTH, Wi-Fi, near-field communication (NFC), ultra-wideband (UWB) and wireless standards, such as IEEE 802.15.4.

In additional further embodiments, the following features are provided, upon pairing, submitting questions regarding data retention. Not only to cars, but IoT devices. At the end of a period, all data is securely deleted. If the vehicle is a personal vehicle, a user may desire to store the data for a longer period of time. The data may be stored in a different data repository, and deleted upon a user exiting the transport. Compartmentalizing the data may be performed to recent and less used. Certain data may need to be expunged, deleted, and/or maintained. The data retention could be tied to a rental/lease agreement for the transport. A privacy mode can be turned on for certain information. Therefore, all content and communications may be encrypted. In one example, an attribute of a contact may be identified, such as always being in privacy mode with that contact. An established privacy mode for a contact can be passed on from one rental transport to another rental transport. A certificate may be issued for a certain period of time, such as 1-2 months, and may be renewed if the device is still good. When connected to the server, an expired certificate can be sent to another server to verify and provide a valid certificate. Recertification can be based on the original certificate. Automatically generating a new certificate before the certificate expires may also be performed. A sub-certificate can be issued based on functionality and can be redirected to another server. The server can send the data as the transport is approached. A transport confirms a user identity, then begins a process to download certificates. A user face or biometric may unlock attributes of the vehicle. A passenger's device may get connected but the owner can establish priority of the system.

FIG. 5A illustrates an example vehicle configuration 500 for managing database transactions associated with a vehicle, according to example embodiments. Referring to FIG. 5A, as a particular transport/vehicle 525 is engaged in transactions (e.g., vehicle service, dealer transactions, delivery/pickup, transportation services, etc.), the vehicle may receive assets 510 and/or expel/transfer assets 512 according to a transaction(s). A transport processor 526 resides in the vehicle 525 and communication exists between the transport processor 526, a database 530, a transport processor 526 and the transaction module 520. The transaction module 520 may record information, such as assets, parties, credits, service descriptions, date, time, location, results, notifications, unexpected events, etc. Those transactions in the transaction module 520 may be replicated into a database 530. The database 530 can be one of a SQL database, an RDBMS, a relational database, a non-relational database, a blockchain, a distributed ledger, and may be on board the transport, may be off board the transport, may be accessible directly and/or through a network, or be accessible to the transport.

FIG. 5B illustrates an example vehicle configuration 550 for managing database transactions conducted among various vehicles, according to example embodiments. The vehicle 525 may engage with another vehicle 508 to perform various actions such as to share, transfer, acquire service calls, etc. when the vehicle has reached a status where the services need to be shared with another vehicle. For example, the vehicle 508 may be due for a battery charge and/or may have an issue with a tire and may be in route to pick up a package for delivery. A transport processor 528 resides in the vehicle 508 and communication exists between the transport processor 528, a database 554, and the transaction module 552. The vehicle 508 may notify another vehicle 525, which is in its network and which operates on its blockchain member service. A transport processor 526 resides in the vehicle 525 and communication exists between the transport processor 526, a database 530, the transport processor 526 and a transaction module 520. The vehicle 525 may then receive the information via a wireless communication request to perform the package pickup from the vehicle 508 and/or from a server (not shown). The transactions are logged in the transaction modules 552 and 520 of both vehicles. The credits are transferred from vehicle 508 to vehicle 525 and the record of the transferred service is logged in the database 530/554 assuming that the blockchains are different from one another, or, are logged in the same blockchain used by all members. The database 554 can be one of a SQL database, an RDBMS, a relational database, a non-relational database, a blockchain, a distributed ledger, and may be on board the transport, may be off board the transport, may be accessible directly and/or through a network.

FIG. 6A illustrates a blockchain architecture configuration 600, according to example embodiments. Referring to FIG. 6A, the blockchain architecture 600 may include certain blockchain elements, for example, a group of blockchain member nodes 602-606 as part of a blockchain group 610. In one example embodiment, a permissioned blockchain is not accessible to all parties but only to those members with permissioned access to the blockchain data. The blockchain nodes participate in a number of activities, such as blockchain entry addition and validation process (consensus). One or more of the blockchain nodes may endorse entries based on an endorsement policy and may provide an ordering service for all blockchain nodes. A blockchain node may initiate a blockchain action (such as an authentication) and seek to write to a blockchain immutable ledger stored in the blockchain, a copy of which may also be stored on the underpinning physical infrastructure.

The blockchain transactions 620 are stored in memory of computers as the transactions are received and approved by the consensus model dictated by the members' nodes. Approved transactions 626 are stored in current blocks of the blockchain and committed to the blockchain via a committal procedure, which includes performing a hash of the data contents of the transactions in a current block and referencing a previous hash of a previous block. Within the blockchain, one or more smart contracts 630 may exist that define the terms of transaction agreements and actions included in smart contract executable application code 632, such as registered recipients, vehicle features, requirements, permissions, sensor thresholds, etc. The code may be configured to identify whether requesting entities are registered to receive vehicle services, what service features they are entitled/required to receive given their profile statuses and whether to monitor their actions in subsequent events. For example, when a service event occurs and a user is riding in the vehicle, the sensor data monitoring may be triggered, and a certain parameter, such as a vehicle charge level, may be identified as being above/below a particular threshold for a particular period of time, then the result may be a change to a current status, which requires an alert to be sent to the managing party (i.e., vehicle owner, vehicle operator, server, etc.) so the service can be identified and stored for reference. The vehicle sensor data collected may be based on types of sensor data used to collect information about vehicle's status. The sensor data may also be the basis for the vehicle event data 634, such as a location(s) to be traveled, an average speed, a top speed, acceleration rates, whether there were any collisions, was the expected route taken, what is the next destination, whether safety measures are in place, whether the vehicle has enough charge/fuel, etc. All such information may be the basis of smart contract terms 630, which are then stored in a blockchain. For example, sensor thresholds stored in the smart contract can be used as the basis for whether a detected service is necessary and when and where the service should be performed.

FIG. 6B illustrates a shared ledger configuration, according to example embodiments. Referring to FIG. 6B, the blockchain logic example 640 includes a blockchain application interface 642 as an API or plug-in application that links to the computing device and execution platform for a particular transaction. The blockchain configuration 640 may include one or more applications, which are linked to application programming interfaces (APIs) to access and execute stored program/application code (e.g., smart contract executable code, smart contracts, etc.), which can be created according to a customized configuration sought by participants and can maintain their own state, control their own assets, and receive external information. This can be deployed as an entry and installed, via appending to the distributed ledger, on all blockchain nodes.

The smart contract application code 644 provides a basis for the blockchain transactions by establishing application code, which when executed causes the transaction terms and conditions to become active. The smart contract 630, when executed, causes certain approved transactions 626 to be generated, which are then forwarded to the blockchain platform 652. The platform includes a security/authorization 658, computing devices, which execute the transaction management 656 and a storage portion 654 as a memory that stores transactions and smart contracts in the blockchain.

The blockchain platform may include various layers of blockchain data, services (e.g., cryptographic trust services, virtual execution environment, etc.), and underpinning physical computer infrastructure that may be used to receive and store new entries and provide access to auditors, which are seeking to access data entries. The blockchain may expose an interface that provides access to the virtual execution environment necessary to process the program code and engage the physical infrastructure. Cryptographic trust services may be used to verify entries such as asset exchange entries and keep information private.

The blockchain architecture configuration of FIGS. 6A and 6B may process and execute program/application code via one or more interfaces exposed, and services provided, by the blockchain platform. As a non-limiting example, smart contracts may be created to execute reminders, updates, and/or other notifications subject to the changes, updates, etc. The smart contracts can themselves be used to identify rules associated with authorization and access requirements and usage of the ledger. For example, the information may include a new entry, which may be processed by one or more processing entities (e.g., processors, virtual machines, etc.) included in the blockchain layer. The result may include a decision to reject or approve the new entry based on the criteria defined in the smart contract and/or a consensus of the peers. The physical infrastructure may be utilized to retrieve any of the data or information described herein.

Within smart contract executable code, a smart contract may be created via a high-level application and programming language, and then written to a block in the blockchain. The smart contract may include executable code that is registered, stored, and/or replicated with a blockchain (e.g., distributed network of blockchain peers). An entry is an execution of the smart contract code, which can be performed in response to conditions associated with the smart contract being satisfied. The executing of the smart contract may trigger a trusted modification(s) to a state of a digital blockchain ledger. The modification(s) to the blockchain ledger caused by the smart contract execution may be automatically replicated throughout the distributed network of blockchain peers through one or more consensus protocols.

The smart contract may write data to the blockchain in the format of key-value pairs. Furthermore, the smart contract code can read the values stored in a blockchain and use them in application operations. The smart contract code can write the output of various logic operations into the blockchain. The code may be used to create a temporary data structure in a virtual machine or other computing platform. Data written to the blockchain can be public and/or can be encrypted and maintained as private. The temporary data that is used/generated by the smart contract is held in memory by the supplied execution environment, then deleted once the data needed for the blockchain is identified.

A smart contract executable code may include the code interpretation of a smart contract, with additional features. As described herein, the smart contract executable code may be program code deployed on a computing network, where it is executed and validated by chain validators together during a consensus process. The smart contract executable code receives a hash and retrieves from the blockchain a hash associated with the data template created by use of a previously stored feature extractor. If the hashes of the hash identifier and the hash created from the stored identifier template data match, then the smart contract executable code sends an authorization key to the requested service. The smart contract executable code may write to the blockchain data associated with the cryptographic details.

FIG. 6C illustrates a blockchain configuration for storing blockchain transaction data, according to example embodiments. Referring to FIG. 6C, the example configuration 660 provides for the vehicle 662, the user device 664 and a server 666 sharing information with a distributed ledger (i.e., blockchain) 668. The server may represent a service provider entity inquiring with a vehicle service provider to share user profile rating information in the event that a known and established user profile is attempting to rent a vehicle with an established rated profile. The server 666 may be receiving and processing data related to a vehicle's service requirements. As the service events occur, such as the vehicle sensor data indicates a need for fuel/charge, a maintenance service, etc., a smart contract may be used to invoke rules, thresholds, sensor information gathering, etc., which may be used to invoke the vehicle service event. The blockchain transaction data 670 is saved for each transaction, such as the access event, the subsequent updates to a vehicle's service status, event updates, etc. The transactions may include the parties, the requirements (e.g., 18 years of age, service eligible candidate, valid driver's license, etc.), compensation levels, the distance traveled during the event, the registered recipients permitted to access the event and host a vehicle service, rights/permissions, sensor data retrieved during the vehicle event operation to log details of the next service event and identify a vehicle's condition status, and thresholds used to make determinations about whether the service event was completed and whether the vehicle's condition status has changed.

FIG. 6D illustrates blockchain blocks 680 that can be added to a distributed ledger, according to example embodiments, and contents of block structures 682A to 682 n. Referring to FIG. 6D, clients (not shown) may submit entries to blockchain nodes to enact activity on the blockchain. As an example, clients may be applications that act on behalf of a requester, such as a device, person or entity to propose entries for the blockchain. The plurality of blockchain peers (e.g., blockchain nodes) may maintain a state of the blockchain network and a copy of the distributed ledger. Different types of blockchain nodes/peers may be present in the blockchain network including endorsing peers, which simulate and endorse entries proposed by clients and committing peers which verify endorsements, validate entries, and commit entries to the distributed ledger. In this example, the blockchain nodes may perform the role of endorser node, committer node, or both.

The instant system includes a blockchain that stores immutable, sequenced records in blocks, and a state database (current world state) maintaining a current state of the blockchain. One distributed ledger may exist per channel and each peer maintains its own copy of the distributed ledger for each channel of which they are a member. The instant blockchain is an entry log, structured as hash-linked blocks where each block contains a sequence of N entries. Blocks may include various components such as those shown in FIG. 6D. The linking of the blocks may be generated by adding a hash of a prior block's header within a block header of a current block. In this way, all entries on the blockchain are sequenced and cryptographically linked together preventing tampering with blockchain data without breaking the hash links. Furthermore, because of the links, the latest block in the blockchain represents every entry that has come before it. The instant blockchain may be stored on a peer file system (local or attached storage), which supports an append-only blockchain workload.

The current state of the blockchain and the distributed ledger may be stored in the state database. Here, the current state data represents the latest values for all keys ever included in the chain entry log of the blockchain. Smart contract executable code invocations execute entries against the current state in the state database. To make these smart contract executable code interactions extremely efficient, the latest values of all keys are stored in the state database. The state database may include an indexed view into the entry log of the blockchain, it can therefore be regenerated from the chain at any time. The state database may automatically get recovered (or generated if needed) upon peer startup, before entries are accepted.

Endorsing nodes receive entries from clients and endorse the entry based on simulated results. Endorsing nodes hold smart contracts, which simulate the entry proposals. When an endorsing node endorses an entry, the endorsing nodes creates an entry endorsement, which is a signed response from the endorsing node to the client application indicating the endorsement of the simulated entry. The method of endorsing an entry depends on an endorsement policy that may be specified within smart contract executable code. An example of an endorsement policy is “the majority of endorsing peers must endorse the entry.” Different channels may have different endorsement policies. Endorsed entries are forward by the client application to an ordering service.

The ordering service accepts endorsed entries, orders them into a block, and delivers the blocks to the committing peers. For example, the ordering service may initiate a new block when a threshold of entries has been reached, a timer times out, or another condition. In this example, blockchain node is a committing peer that has received a data block 682A for storage on the blockchain. The ordering service may be made up of a cluster of orderers. The ordering service does not process entries, smart contracts, or maintain the shared ledger. Rather, the ordering service may accept the endorsed entries and specifies the order in which those entries are committed to the distributed ledger. The architecture of the blockchain network may be designed such that the specific implementation of ‘ordering’ (e.g., Solo, Kafka, BFT, etc.) becomes a pluggable component.

Entries are written to the distributed ledger in a consistent order. The order of entries is established to ensure that the updates to the state database are valid when they are committed to the network. Unlike a cryptocurrency blockchain system (e.g., Bitcoin, etc.) where ordering occurs through the solving of a cryptographic puzzle, or mining, in this example the parties of the distributed ledger may choose the ordering mechanism that best suits that network.

Referring to FIG. 6D, a block 682A (also referred to as a data block) that is stored on the blockchain and/or the distributed ledger may include multiple data segments such as a block header 684A to 684 n, transaction specific data 686A to 686 n, and block metadata 688A to 688 n. It should be appreciated that the various depicted blocks and their contents, such as block 682A and its contents are merely for purposes of an example and are not meant to limit the scope of the example embodiments. In some cases, both the block header 684A and the block metadata 688A may be smaller than the transaction specific data 686A, which stores entry data; however, this is not a requirement. The block 682A may store transactional information of N entries (e.g., 100, 500, 1000, 2000, 3000, etc.) within the block data 690A to 690 n. The block 682A may also include a link to a previous block (e.g., on the blockchain) within the block header 684A. In particular, the block header 684A may include a hash of a previous block's header. The block header 684A may also include a unique block number, a hash of the block data 690A of the current block 682A, and the like. The block number of the block 682A may be unique and assigned in an incremental/sequential order starting from zero. The first block in the blockchain may be referred to as a genesis block, which includes information about the blockchain, its members, the data stored therein, etc.

The block data 690A may store entry information of each entry that is recorded within the block. For example, the entry data may include one or more of a type of the entry, a version, a timestamp, a channel ID of the distributed ledger, an entry ID, an epoch, a payload visibility, a smart contract executable code path (deploy tx), a smart contract executable code name, a smart contract executable code version, input (smart contract executable code and functions), a client (creator) identify such as a public key and certificate, a signature of the client, identities of endorsers, endorser signatures, a proposal hash, smart contract executable code events, response status, namespace, a read set (list of key and version read by the entry, etc.), a write set (list of key and value, etc.), a start key, an end key, a list of keys, a Merkel tree query summary, and the like. The entry data may be stored for each of the N entries.

In some embodiments, the block data 690A may also store transaction specific data 686A, which adds additional information to the hash-linked chain of blocks in the blockchain. Accordingly, the data 686A can be stored in an immutable log of blocks on the distributed ledger. Some of the benefits of storing such data 686A are reflected in the various embodiments disclosed and depicted herein. The block metadata 688A may store multiple fields of metadata (e.g., as a byte array, etc.). Metadata fields may include signature on block creation, a reference to a last configuration block, an entry filter identifying valid and invalid entries within the block, last offset persisted of an ordering service that ordered the block, and the like. The signature, the last configuration block, and the orderer metadata may be added by the ordering service. Meanwhile, a committer of the block (such as a blockchain node) may add validity/invalidity information based on an endorsement policy, verification of read/write sets, and the like. The entry filter may include a byte array of a size equal to the number of entries in the block data 610A and a validation code identifying whether an entry was valid/invalid.

The other blocks 682B to 682 n in the blockchain also have headers, files, and values. However, unlike the first block 682A, each of the headers 684A to 684 n in the other blocks includes the hash value of an immediately preceding block. The hash value of the immediately preceding block may be just the hash of the header of the previous block or may be the hash value of the entire previous block. By including the hash value of a preceding block in each of the remaining blocks, a trace can be performed from the Nth block back to the genesis block (and the associated original file) on a block-by-block basis, as indicated by arrows 692, to establish an auditable and immutable chain-of-custody.

The above embodiments may be implemented in hardware, in a computer program executed by a processor, in firmware, or in a combination of the above. A computer program may be embodied on a computer readable medium, such as a storage medium. For example, a computer program may reside in random access memory (“RAM”), flash memory, read-only memory (“ROM”), erasable programmable read-only memory (“EPROM”), electrically erasable programmable read-only memory (“EEPROM”), registers, hard disk, a removable disk, a compact disk read-only memory (“CD-ROM”), or any other form of storage medium known in the art.

An exemplary storage medium may be coupled to the processor such that the processor may read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an application specific integrated circuit (“ASIC”). In the alternative, the processor and the storage medium may reside as discrete components. For example, FIG. 7 illustrates an example computer system architecture 700, which may represent or be integrated in any of the above-described components, etc.

FIG. 7 is not intended to suggest any limitation as to the scope of use or functionality of embodiments of the application described herein. Regardless, the computing node 700 is capable of being implemented and/or performing any of the functionality set forth hereinabove.

In computing node 700 there is a computer system/server 702, which is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 702 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like.

Computer system/server 702 may be described in the general context of computer system-executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 702 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.

As shown in FIG. 7 , computer system/server 702 in cloud computing node 700 is shown in the form of a general-purpose computing device. The components of computer system/server 702 may include, but are not limited to, one or more processors or processing units 704, a system memory 706, and a bus that couples various system components including system memory 706 to processor 704.

The bus represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.

Computer system/server 702 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 702, and it includes both volatile and non-volatile media, removable and non-removable media. System memory 706, in one embodiment, implements the flow diagrams of the other figures. The system memory 706 can include computer system readable media in the form of volatile memory, such as random-access memory (RAM) 708 and/or cache memory 710. Computer system/server 702 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, memory 706 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to the bus by one or more data media interfaces. As will be further depicted and described below, memory 706 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of various embodiments of the application.

Program/utility, having a set (at least one) of program modules, may be stored in memory 706 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules generally carry out the functions and/or methodologies of various embodiments of the application as described herein.

As will be appreciated by one skilled in the art, aspects of the present application may be embodied as a system, method, or computer program product. Accordingly, aspects of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present application may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.

Computer system/server 702 may also communicate with one or more external devices via an I/O device 712 (such as an I/O adapter), which may include a keyboard, a pointing device, a display, a voice recognition module, etc., one or more devices that enable a user to interact with computer system/server 702, and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 702 to communicate with one or more other computing devices. Such communication can occur via I/O interfaces of the device 712. Still yet, computer system/server 702 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via a network adapter. As depicted, device 712 communicates with the other components of computer system/server 702 via a bus. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 702. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

Although an exemplary embodiment of at least one of a system, method, and non-transitory computer readable medium has been illustrated in the accompanied drawings and described in the foregoing detailed description, it will be understood that the application is not limited to the embodiments disclosed, but is capable of numerous rearrangements, modifications, and substitutions as set forth and defined by the following claims. For example, the capabilities of the system of the various figures can be performed by one or more of the modules or components described herein or in a distributed architecture and may include a transmitter, receiver or pair of both. For example, all or part of the functionality performed by the individual modules, may be performed by one or more of these modules. Further, the functionality described herein may be performed at various times and in relation to various events, internal or external to the modules or components. Also, the information sent between various modules can be sent between the modules via at least one of: a data network, the Internet, a voice network, an Internet Protocol network, a wireless device, a wired device and/or via plurality of protocols. Also, the messages sent or received by any of the modules may be sent or received directly and/or via one or more of the other modules.

One skilled in the art will appreciate that a “system” could be embodied as a personal computer, a server, a console, a personal digital assistant (PDA), a cell phone, a tablet computing device, a smartphone or any other suitable computing device, or combination of devices. Presenting the above-described functions as being performed by a “system” is not intended to limit the scope of the present application in any way but is intended to provide one example of many embodiments. Indeed, methods, systems and apparatuses disclosed herein may be implemented in localized and distributed forms consistent with computing technology.

It should be noted that some of the system features described in this specification have been presented as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, graphics processing units, or the like.

A module may also be at least partially implemented in software for execution by various types of processors. An identified unit of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions that may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together but may comprise disparate instructions stored in different locations that when joined logically together, comprise the module and achieve the stated purpose for the module. Further, modules may be stored on a computer-readable medium, which may be, for instance, a hard disk drive, flash device, random access memory (RAM), tape, or any other such medium used to store data.

Indeed, a module of executable code could be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.

It will be readily understood that the components of the application, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the detailed description of the embodiments is not intended to limit the scope of the application as claimed but is merely representative of selected embodiments of the application.

One having ordinary skill in the art will readily understand that the above may be practiced with steps in a different order, and/or with hardware elements in configurations that are different than those which are disclosed. Therefore, although the application has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent.

While preferred embodiments of the present application have been described, it is to be understood that the embodiments described are illustrative only and the scope of the application is to be defined solely by the appended claims when considered with a full range of equivalents and modifications (e.g., protocols, hardware devices, software platforms etc.) thereto. 

What is claimed is:
 1. A method, comprising: unencrypting, by the transport processor, encrypted data associated with a first biometric and a transport occupant based on a verification of a second biometric, associated with a transport occupant; and providing, by the transport processor, the unencrypted data to a user interface inside the transport; wherein additional biometric data is detected; wherein whether the additional biometric data is based on one or more of a time threshold and a distance threshold; wherein the unencrypted data comprises a sensitive portion and a non-sensitive portion related to the transport occupant; and wherein the transport processor deletes the sensitive portion as the sensitive portion is being provided, and deleting the non-sensitive portion after a period of time associated with the second biometric has lapsed.
 2. The method of claim 1, comprising: determining only the occupant is in the transport.
 3. The method of claim 2, wherein the deleting the non-sensitive portion after the period of time, associated with the second biometric has lapsed, is performed when the second biometric is not received by the transport after the period of time.
 4. The method of claim 1, comprising: wherein the second biometric is a time continuum of the first biometric, wherein the time continuum is a predetermined period of time during which the first and second biometrics must be identified by the transport processor.
 5. The method of claim 1, comprising determining one or more additional occupants are present in the transport when the received data is encrypted; providing the non-sensitive portion of the unencrypted data to a vehicle interface; determining, at a later time, only the occupant is in the transport; and providing the sensitive portion of the data to the occupant.
 6. The method of claim 1, comprising receiving, by the transport, a validation of the continuum from at least one component, wherein the validation comprises a blockchain consensus between a peer group consisting of the transport and the at least one component.
 7. The method of claim 6, comprising executing a smart contract, by the transport, to record the validation and the at least one component on a blockchain based on the blockchain consensus.
 8. A transport, comprising: a processor configured to: unencrypt, by the transport processor, encrypted data associated with a first biometric and a transport occupant based on a verification of a second biometric, associated with a transport occupant; and provide, by the transport processor, the unencrypted data to a user interface inside the transport; wherein additional biometric data is detected; wherein whether the additional biometric data is based on one or more of a time threshold and a distance threshold; wherein the unencrypted data comprises a sensitive portion and a non-sensitive portion related to the transport occupant; and wherein the transport processor deletes the sensitive portion as the sensitive portion is provided, and deletes the non-sensitive portion after a period of time associated with the second biometric has lapsed.
 9. The transport of claim 8, wherein the processor is further configured to: determine only the occupant is in the transport.
 10. The transport of claim 9, wherein the deletion of the non-sensitive portion after the period of time, associated with the second biometric has lapsed, is performed when the second biometric is not received by the transport after the period of time.
 11. The transport of claim 8, comprising: wherein the second biometric is a time continuum of the first biometric, wherein the time continuum is a predetermined period of time during which the first and second biometrics must be identified by the transport processor.
 12. The transport of claim 8, wherein the processor is further configured to: determine one or more additional occupants are present in the transport when the received data is encrypted; provide the non-sensitive portion of the unencrypted data to a vehicle interface; determine, at a later time, only the occupant is in the transport; and provide the sensitive portion of the data to the occupant.
 13. The transport of claim 8, comprising: receive a validation of the continuum from at least one component, wherein the validation comprises a blockchain consensus between a peer group that consists of the transport and the at least one component.
 14. The transport of claim 13, wherein the processor is further configured to: execute a smart contract to record the validation and the at least one component on a blockchain based on the blockchain consensus.
 15. A non-transitory computer readable medium comprising instructions, that when read by a processor, cause the processor to perform: unencrypting, by the transport processor, encrypted data associated with a first biometric and a transport occupant based on a verification of a second biometric, associated with a transport occupant; and providing, by the transport processor, the unencrypted data to a user interface inside the transport; wherein additional biometric data is detected; wherein whether the additional biometric data is based on one or more of a time threshold and a distance threshold; wherein the unencrypted data comprises a sensitive portion and a non-sensitive portion related to the transport occupant; and wherein the transport processor deletes the sensitive portion as the sensitive portion is being provided, and deleting the non-sensitive portion after a period of time associated with the second biometric has lapsed.
 16. The non-transitory computer readable medium of claim 15, wherein the processor is further configured to perform: determining only the occupant is in the transport.
 17. The non-transitory computer readable medium of claim 16, wherein the deleting the non-sensitive portion after the period of time, associated with the second biometric has lapsed, is performed when the second biometric is not received by the transport after the period of time.
 18. The non-transitory computer readable medium of claim 15, wherein the processor is further configured to perform: wherein the second biometric is a time continuum of the first biometric, wherein the time continuum is a predetermined period of time during which the first and second biometrics must be identified by the transport processor.
 19. The non-transitory computer readable medium of claim 15, wherein the processor is further configured to perform: determining one or more additional occupants are present in the transport when the received data is encrypted; providing the non-sensitive portion of the unencrypted data to a vehicle interface; determining, at a later time, only the occupant is in the transport; and providing the sensitive portion of the data to the occupant.
 20. The non-transitory computer readable medium of claim 15, wherein the processor is further configured to perform: receiving, by the transport, a validation of the continuum from at least one component, wherein the validation comprises a blockchain consensus between a peer group consisting of the transport and the at least one component. 